Method of communication between reduced functionality devices in an ieee 802.15.4 network

ABSTRACT

In a 802.15.4 network, each reduced functionality device (RFD) is permitted to communicate with only an assigned full function device (FFD). The present invention allows each of the RFDs to communicate with another RFD upon the RFD determining that the local FFD assigned to the RFD is inoperable or unable to communicate. Under emergency conditions, the RFD is able to communicate with a closely located RFDs such that the closely located RFDs can receive and respond to an emergency situation and/or repeat the message. To satisfy the 802.15.4 standards, communication between the RFDs is allowed only during emergency conditions and when the FFD is inoperative. A comprehensive test procedure is included to insure the integrity of the system is preserved at all times.

CROSS REFERENCE TO RELATED APPLICATION

The present application is based on and claims priority to U.S.Provisional Application Ser. No. 60/621,180, filed Oct. 22, 2004.

BACKGROUND OF THE INVENTION

IEEE standard 802.15.4 was developed to standardize communicationbetween devices operating within a local area network (LAN). The IEEEstandard was targeted at home, building and industrial automation andcontrols, consumer electronics, PC profiles and medical monitoring. Thestandards define the interoperability, certification testing andbranding of devices that operate within the IEEE standard.

In a standard 802.15.4 network, the network includes three differentdevice types. The first device type is classified as a networkcoordinator and maintains overall network knowledge.

The second type of device type in a 802.15.4 network is referred as afull function device (FFD). Each of the FFDs has full communicationfunctionality with all the features required by the 802.15.4 standard.Further, the FFD includes additional memory and computing power thatmakes it ideal for acting as a network router. Each of the FFDs is ableto communicate with both the network coordinator and lower level devicesreferred to as reduced function devices (RFDs).

The third type of device included in the 802.15.4 network is a reducedfunction device (RFD) that is designed to communicate with a single FFD.Each RFD includes limited functionality as specified by the 802.15.4standard to limit the cost and complexity of the RFD. As required by theliteral interpretation 802.15.4 standard, each RFD communicates solelywith an FFD and cannot communicate with other RFDs.

The 802.15.4 network is contemplated as being particularly desirable intransmitting information within a building automation system. Forexample, each of the RFDs could be an environmental sensor, smokedetector, motion detector or any other kind of monitoring equipment thatis required for monitoring and controlling the operation of a building.

Although the 802.15.4 networking configuration has worked well, aproblem can occur if and when a FFD is rendered inoperative or is out ofcommunications, such as during a power interruption. FFDs are generallydesigned to be online at all times and therefore are normally linepowered. RFDs, by design, are not always online and typically arebattery powered. When one of the FFDs is removed from the network, suchas during the power loss to the FFD, the RFDs associated with thedisabled FFD are unable to communicate information across the networkunless they are within communication range of another FFD. If most orall of the FFDs are removed from the network (as might be the caseduring a power outage), then all of the RFDs will be unable tocommunicate a detected alarm condition. This drawback can becomeimportant when the RFDs are safety devices, such as smoke detectors.

Therefore, a need exists for an improved communication method operatingwithin the 802.15.4 standard or any extension thereof, that allows forcommunication during emergency situations or when one or more of theFFDs has been rendered inoperative.

SUMMARY OF THE INVENTION

The present invention relates to a method of enhancing the communicationbetween reduced functionality devices (RFDs) and full functional devices(FFDs) in a communication network, such as a network operated under theIEEE 802.15.4 standard. The method of the invention enhancescommunications particularly when one of the FFDs in the network has beenrendered inoperative, such as during a power failure.

A standard network configured using IEEE standard 802.15.4 includes aplurality of RFDs that each include a wireless transceiver. Each of theRFDs is positioned such that the RFD is in communication range with anassigned FFD. In a typical 802.15.4 network, each of the RFDscommunicates directly to its assigned FFD and responds only to messagesreceived from the assigned FFD.

In accordance with the present invention, each of the RFDs is activatedduring a predetermined activation period. During the activation period,the RFD attempts to establish communication with the FFD to which it isassigned. If the RFD is unsuccessful in establishing communication withthe FFD, the RFD enters into an “orphaned” state. The RFD enters intothe orphaned state only upon the failure to establish communication withthe assigned FFD.

After the RFD has entered into the orphaned state, the wirelesstransceiver of the RFD optionally remains active to transmit any alarmmessage and receive any messages from other RFDs within communicationrange of the RFD. Although the continued activation of the wirelesstransceiver of the RFD drains the power of the battery contained withinthe RFD, the RFD remains active during what may be an emergencysituation.

During the time that the RFD is in an orphaned state and the wirelesstransceiver remains active or up waking/activation, the RFD can receivemessages from either other RFDs or FFDs other than the FFD to which theRFD is assigned. When the RFD is in the orphaned state and receives amessage, the RFD is allowed to respond to or relay the message asrequired. For example, if the RFD is a hazardous condition detector andthe message received is a “smoke detected” message from anotherhazardous condition detector, the RFD is allowed to generate an alarmsignal.

In addition to the orphan state operating conditions above, an RFD whilein the orphan state can transmit an orphan state indicator as itattempts to rejoin with its assigned FFD. The orphan state indicatorwill alert other RFDs and FFDs that might receive the signal that an RFDhas been orphaned and is seeking to join the network through analternative temporary path. As a result, if an RFD wakes up andinitiates a communications session with its assigned FFD and in theprocess receives an orphan state indicator from a near by RFD, the RFDcan enter a temporary relay mode state and communicate with both theorphaned RFD and its assigned FFD to complete a temporary communicationpath over which the orphaned RFD can communicate with an operationalFFD.

In a like fashion, if an orphaned RFD detects other RFDs transmitting anorphan state indicator, the orphaned RFD can respond andintercommunicate with other RFDs in an attempt to form an alternate pathback to an operational FFD. Once associated with an alternative FFD orupon being relayed through another RFD, the orphaned RFD will assume an“orphaned but connected state”.

If an operational FFD can not be located, the orphaned RFDs willoptionally remain in communications with one another. This “orphaned andrelaying but not connected state”, permits RFDs to relay status andconditional information among themselves until an operational FFDreturns to the system.

When an RFD's primary FFD is lost and subsequently returns to thenetwork, the RFDs assigned to the FFD will drop any temporaryalternative communication path that may have been established in theorphan mode with alternative FFDs and rejoin the primary FFD. The RFDsin this case, however, will not automatically drop any relayrelationships they may have developed with other RFDs until those RFDsdrop their relay relationships with them. This will only occur when the“relay dependent” RFDs primary FFD or an alternative non-primary FFDcommunications path is established. At this point, the “relay dependent”RFD will no longer need to depend on the RFD that is linked to its FFDfor relay services and the relaying RFD can return to its normal mode asa standard operational RFD with an assigned primary FFD relationship.

In accordance with the present invention, an RFD will always attemptfirst to communicate with its primary FFD. If the communication isunsuccessful, the RFD will next attempt to join a non-primary FFD as anorphaned RFD until its primary FFD returns. The next level of recoveryfor an orphaned RFD can be to join with an RFD that has a communicationspath operational with either a primary or non-primary FFD in an orphanedbut connected mode. In this case, the RFD will join with another RFD,which will relay its information to an FFD that is operational but notthe primary FFD. Lastly, an orphaned RFD can form a relationship withother orphaned RFDs that have no linkage to an active FFD in the networkto permit intercommunications in an “orphaned and relaying but notconnected” mode.

In addition to responding to a received alarm message in an orphanedstate, upon receiving the alarm signal, the orphaned RFD will remainactive and retransmit the alarm message to other RFDs or non-primaryFFDs within wireless communication range. The communication directlybetween the RFDs allows the RFDs to respond to an emergency conditioneven if the assigned FFD or any alternates have been renderedinoperative, such as through the interruption of power to the FFD.

While the RFD is in its orphaned state, the RFD continues to attempt toestablish communication with its assigned FFD. Once the RFD establishescommunication with its assigned FFD, the RFD exits the orphaned stateand is then restricted from directly responding to any messages receivedfrom other RFDs, except as noted when other orphaned RFDs are dependenton it in a “relay state”. When the RFD is no longer in the orphan stateor the “relay state”, the RFD will return to the “sleep” state and canrespond only to messages from the assigned FFD, in accordance with theIEEE 802.15.4 standard.

During operation of the communication network, an FFD can carry out atest procedure on regularly schedule intervals. During the testprocedure, the FFD causes each individual RFD to generate a test signal.After the test signal has been generated by the transmitting RFD, theother RFDs in the communication network act as signal receivers toreceive and detect the test signal. Each of the receiving RFDs provideinput to the FFD conducting the test on whether the test signal has beenreceived and the quality of the signal. This test procedure is repeatedfor each RFD individually.

If during this test process, when an RFD transmits its test signal noother RFD receives the signal, the assigned FFD generates an alarmcondition indicating that the transmitting RFD is unable to communicatewith at least one other RFD. Such a situation may occur when the batterywithin the RFD is weak or if something in the communication path isblocking the signal generated by the transmitting RFD making it orphanedwith no alternative route when the FFD is not available. The testprocedure assures that each RFD is in communication range with at leastone other RFD so that should the FFD fail, the RFD can still communicatean emergency message to another RFD. It is important to note that in aFFD failure state, each RFD should not only be capable of communicatingwith another RFD, but there should be a clear path over which all RFDcan be interconnected. This assumes that in a network of more than twoRFD's, an RFD that can only communicate with one other RFD must rely onthat RFD to relay data to other RFDs. As a result, the relaying RFD inthis case should be capable of communicating with at least one other RFDand so on until a complete interconnection of RFDs is accomplished.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings illustrate the best mode presently contemplated in carryingout the invention. In the drawings:

FIG. 1 is a schematic illustration of a standard IEEE 802.15.4 networkin which the reduced functionality devices (RFDs) are shown by referencenumbers A-L and the full function devices (FFDs) are labeled withreference numerals 1-5;

FIG. 2 is a schematic illustration of an 802.15.4 network in which theRFDs are allowed to communicate with each other and at least onealternate FFDs upon a communication failure to the FFD primarilyassigned to the RFDs;

FIG. 3 is a flow chart illustrating the operation of each RFD within the802.15.4 network;

FIG. 4 is a schematic illustration of an 802.15.4 network in which eachof the FFDs has been rendered inoperative; and

FIG. 5 is a schematic illustration of a test message generated by one ofthe RFDs and received by multiple other RFDs and FFDs.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As illustrated in FIG. 1, the RFDs are shown by reference letters A-L.In the embodiment illustrated, each of the RFDs communicates to asingle, full function device (FFD). Each of the FFDs shown in FIG. 1 islabeled with the reference numerals 1-5. In the example configuration ofFIG. 1, the RFDs A, B and C are assigned to FFD 1 and are able tocommunicate only to the FFD 1. The FFD 1 is able to communicate to asecond FFD 2.

In the standard embodiment of an 802.15.4 network, as shown in FIG. 1,should the RFD A need to transmit information to the RFD B, then RFD Atransmits data first to the to FFD 1 and FFD 1 in turntransmits/forwards the message to RFD B. This multi-node communicationis required, since both of the RFDs A and B are typically in an off,sleeping mode and are awake to accept messages only on an intermittentbasis to conserve battery life. Thus, even if the RFD B was within theRF transmission range of the RFD A, the RFD A is unsure as to when theRFD B will be awake and able to receive a message. However, FFD 1 isactive at all times and is aware of the schedule of the associated RFDsA, B and C such that the FFD 1 is able to transmit the receivedinformation from the RFD A to the RFD B.

As can be understood by the above description, the limited communicationability between the RFDs within the 802.15.4 network of FIG. 1 imposes asevere constraint on the network communication and design. Further, therestricted communication results in the requirement that each of theFFDs include some type of battery backup for cases where there may be apower outage. The battery backup ensures that the network continues tooperate properly and can communicate messages throughout the networkshould a power outage occur. For example, if each of the RFDs A, B and Care hazardous condition detectors, such as smoke detectors, carbonmonoxide detectors or combination units, if the power is disrupted tothe FFD 1, it may be important for the RFDs A, B and C to be able tocommunicate with each other should one of the RFDs detect an alarmcondition. If the FFD 1 is inactive and unable to communicate the alarmsignals between the RFDs A, B and C, an alarm condition in one room of ahome may not be relayed to an alarm device in another room.

In order to address the above identified problem, it is necessary toloosely interpret the 802.15.4 standard to allow each of the RFDs toaccept messages from other devices besides their assigned FFDs during anarrowly defined condition. As an example, the RFDs A, B and C will beconfigured to accept messages from each other and alternate FFDs whenthe primary FFD is not available. In order to satisfy the 802.15.4standard, the present invention will allow the RFDs to accept messagesfrom devices other than the assigned FFD only under well constrainedcircumstances and in specifically defined situations, the details ofwhich follow.

Referring now to FIG. 2, in accordance with the present invention, afterone of the RFDs (A-L) has failed to communicate with its assigned FFD(1-5), and therefore has transitioned to an “orphaned state” as definedby the 802.15.4 standard, the RFD can remain active and then would beable to accept messages from devices other than the assigned FFD. Duringthis extended emergency receiving time, if the RFD receives a broadcastmessage, the RFD will accept the message and process the message. As anexample, if the RFD A is a hazardous condition detector, such as a smokedetector located within a building, the RFD A will, upon the detectionof smoke, transmit an alarm signal to its associated FFD 1. Duringnormal operation, the FFD 1 would then relay this message to the otherRFDs B and C.

If the communication link between RFD A and FFD 1 is broken, as shown inFIG. 2, the RFD A enters an “orphaned” state and will continue totransmit the message, which may be received by the RFDs B and C. Whenthe RFDs B and C awaken, the RFDs B and C will first attempt tocommunicate to the FFD 1. Once the RFDs B and C determine that FFD 1 isunavailable, the RFDs B and C will be allowed to receive messages fromany transmitting RFD, such as RFD A, and process it. For example, if theRFD A is transmitting a “smoke detected” message, RFD B will receivethis message directly from the RFD A and relay the message to RFD C,resulting in all three RFDs generating an audible alarm. Thus, the RFDsoperating in accordance with the present invention will respond to adetected emergency in a situation that would not have otherwisegenerated the desired response in accordance with operation under the802.15.4 standard.

In addition, upon receipt of the emergency message, both of the RFDs Band C will broadcast the message to any other devices within RF range.As shown in FIG. 2, FFD 2 will receive and respond to the message fromthe RFD C, passing the message on to other RFDs in the network. In FIG.4 where all of the FFDs are disabled, RFD C will communicate directlywith RFD E which will relay the message to other orphaned but linkedRFDs, propagating the alarm signal. To be clear, the messages are notunicast to each of the other RFDs in the network, but instead arebroadcast and therefore “flood” across the network.

It is anticipated that the alternate transmission mechanism of thepresent invention will be used only during emergency situations. TheRFDs, which would normally be sleeping or only transmitting on a veryinfrequent basis, will continue to transmit broadcast packets constantlyuntil the emergency situation is resolved or the device is shutdown.

Although it is understood that the transmission mechanism of the presentinvention will have a negative impact on the battery life of the RFDs(FIG. 4), battery life is a secondary consideration during an emergencysituation. It is much more desirable that the RFD detecting theemergency situation will continue to transmit the message at the expenseof battery life as needed to ensure the safety of all premise occupants.

The result of the alternative communication configuration of the presentinvention is that even during a power outage affecting the FFDs (FIG.4), the battery powered RFDs will be able to communicateimportant/critical/emergency information throughout the network.

As discussed in detail above, the devices in the 802.15.4 network areallowed to “break” the 802.15.4 standard only under well constrained andlimited situations. Specifically, each of the RFDs is allowed tocommunicate with a device other than its assigned FFD only after it hastransitioned to an “orphaned state” and generally only when the RFDreceives a broadcast alarm message.

Referring now to FIG. 3, when the RFD awakens at its normally scheduledinterval, as shown by step 110, the RFD attempts to communicate with itsassigned, local FFD as shown in step 112. If the RFD is able tocommunicate with its FFD, the RFD receives messages from the FFD andresponds as desired, as shown in step 115. As an example, if the RFDreceives an alarm message from the local FFD, the RFD will generate itslocal alarm as required. In addition to receiving messages from the FFD,the RFD also transmits information and messages to the FFD in step 117.As an example, if the RFD is detecting smoke, the RFD will send thismessage to the FFD so that the FFD can relay the signal to other devicesin the network.

If the communication between the RFD and its local FFD fails in step114, the RFD enters into an orphaned state, as shown in step 116.Although the 802.15.4 standard contemplates each of the RFDs enteringinto an orphaned state upon the failure to communicate with the localFFD, in accordance with the present invention, when the RFD is in theorphaned state, the RFD listens to determine whether any messages arereceived from other RFDs or remote FFDs, as illustrated in step 118. Themessages received from the other RFDs or remote FFDs may be alarmconditions or other messages being transmitted by the remote devices.

As illustrated by step 120, if the RFD detects any message from anotherRFD or a remote FFD, the RFD is permitted to process and react to themessage as required. For example, if each of the RFDs are smokedetectors, the RFD may receive a smoke alarm signal from one of theother RFDs and can then activate the alarm within the RFD. In addition,the RFD is allowed to retransmit the message, thereby passing themessage to other RFDs or FFDs in wireless communication range with theRFD.

After responding to the message or retransmitting the message, the RFDagain attempts to communicate with the local FFD in step 112. Once theRFD is able to communication with its local, assigned FFD, the RFD willexit the orphaned state and thus be prevented from responding tomessages from other devices other than its assigned, local FFD, asrequired by the 802.15.4 standards.

It is preferred that under the 802.15.4 standard an FFD maintainCommunications Quality of Service (CQOS) statistics for their associatedRFD's. This is done to ensure that any RFD is not entering the orphanstate as a result of poor signal quality following its initialinstallation or any time thereafter. When the signal quality between theFFD and an RFD is marginal or the FFD detects a diminished CQOS at anytime, an alert is generated by the FFD of a type and in a manner tomaintain an acceptable level of integrity of the system. This featureensures the communications network between devices is maintained at thehighest levels and that a battery powered RFD only functions in theorphan mode during true emergencies.

In addition, to ensure that an RFD is able to intercommunicate withother RFDs during an emergency or when their assigned FFD isunavailable, a test sequence initiate by the FFD is part of thepreferred implementation. This optional test procedure is integratedinto the FFD on a scheduled and/or on demand basis. The test procedurecauses the FFD to cause each of the RFD's to stay online during the testprocess. During the test procedure, the FFD causes each of theindividual RFDs to transmit a test message as is illustrated in FIG. 5.In this illustration, FFD 4 has instructed all RFDs and other FFDs thatit is conducting a test of the network. The FFD4 then requests that RFDI initiate a test transmission, which is detected in the illustration byRFDs C, E & K as well as FFDs 4 & 2. After the test signal has beengenerated by the first, transmitting RFD, the other RFDs in thecommunication network act as signal receivers to receive and detect thetest signal. Each of the receiving RFDs and FFDs notify the FFDconducting the test that they have received the test signal along withany other data that may be needed by the FFD. The FFD optionally recordsthis information into a non-volatile storage location. The test resultsfrom each RFD's test message may also be sent to the sending RFD whereit may be stored for future reference in emergency situations. This testprocedure is repeated for each of the RFDs individually.

If no other RFD in the group detects the transmission, the FFD cangenerate an alarm condition indicating that the transmitting RFD isunable to communicate with at least one other RFD. This procedure isessential in installations that are required to maintain a robust andreliable network under all conditions. The failure for one of the RFDsto communicate with at least one other RFD or FFD can occur when thebattery of the RFD has been depleted or some obstruction or other factoris corrupting the communication pathway. In any of these cases, thesignal generated by the transmitting RFD can no longer be received byone of the other RFDs or FFDs in the network. The test procedure ensuresthat each RFD is in communication range with at least one other RFD sothat should all FFDs fail, the RFDs can still communicate an emergencymessage to one another. This test procedure insures that under emergencyconditions, the integrity of the network will be preserved.

If no other RFD in the group detects the transmission, the FFD generatesan alarm condition indicating that the transmitting RFD is unable tocommunicate with at least one other RFD. This procedure is essential inall installations to maintain a robust and reliable network under allconditions. The failure for one of the RFDs to communicate with at leastone other RFD can occur when the battery within either of the RFDs hasbeen depleted or if some other parameter in the communication pathwayhas changed such that the signal generated by the transmitting RFD canno longer be received or one of the other RFDs in the network. The testprocedure ensures that each RFD is in communication range with at leastone other RFD so that should the FFD fail, the RFD can still communicatean emergency message to another RFD. This test procedure insures thatunder emergency conditions, the integrity of the network will bepreserved.

It is important to note that in a FFD failure state (FIG. 4), each RFDmust not only be capable of communicating with another RFD, but theremust be a clear path over which all RFDs can be interconnected. Thisassumes that in a network of more than two RFDs, an RFD that can onlycommunicate with one other RFD must rely on that RFD to relay data toother RFDs. As a result, the relaying RDF in this case must be capableof communicating with at least one other RFD and so on until a completeinterconnection of RFD's is accomplished

1-17. (canceled)
 18. A method of operating a communication networkincluding a full functional device (FFD) having a wireless transceiverand a plurality of reduced function devices (RFDs) each having awireless transceiver and assigned to the FFD, the method comprising thesteps of: positioning the RFDs such that each RFD is in communicationrange with the FFD and at least one other RFD; activating the FFD toperform a test procedure during which the FFD causes each of the RFDs totransmit a test message and each other RFD confirms receipt of the testmessage to the FFD; and activating an alarm when the test signal fromany RFD is not received by any of the other RFDs.
 19. The method ofclaim 18 wherein the communication network is operated under IEEEstandard 802.15.4.
 20. The method of claim 18 wherein the identity ofeach RFD and FFD receiving the test message from the RFD transmittingthe test message is stored in the memory of the FFD conducting the test.21. The method of claim 18 wherein the identity of each RFD and FFDreceiving the test message from the RFD transmitting the test message isstored in the memory of the RFD sending the test message.
 22. The methodof claim 21 where the data stored in memory contains signal strengthdata associated with RFD and FFD reporting.
 23. The method of claim 18wherein each RFD is a hazardous condition detector including an internalbattery.
 24. The method of claim 18 wherein the wireless transceiver ofeach RFD is activated during a predetermined activation period, whereinthe RFD attempts to establish communication to the FFD during theactivation period; determining whether communication has beenestablished between the RFD and the FFD, wherein the RFD enters anorphaned state upon the failure to establish communication with the FFD;continuing to operate the transceiver of the RFD to receive messagesfrom either the FFD or other RFDs when the RFD is in the orphaned state;and allowing the RFD to respond to the messages received from the otherRFDs only when the RFD is in the orphaned state.